This repository was archived by the owner on Jan 17, 2023. It is now read-only.
WebDav Response Namespace not always 'D' #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I removed the inNamespace:@"D" for the AFWebDAVMultiStatusResponse because the response does not always use the "D" Namespace I found that Microsoft servers use the namespace "a". Information on Microsoft webdav https://msdn.microsoft.com/en-us/library/ms879496(v=exchg.65).aspx I testested with an "a" namespace and a "D" namespace server and there were no issues.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I removed the inNamespace:@"D" for the AFWebDAVMultiStatusResponse because the response does not always use the "D" Namespace I found that Microsoft servers use the namespace "a". Information on Microsoft webdav https://msdn.microsoft.com/en-us/library/ms879496(v=exchg.65).aspx
I testested with an "a" namespace and a "D" namespace server and there were no issues.